Code Owners

@ivandev0, it would be very helpful to place a reference to the reasons for removing IR (de)serialization into the commit messages, a link to the corresponding YT issue, or just a few words. I have no active context about it, so it's difficult to make a meaningful approval. But even if I did, such a reference would still benefit the future maintenance.

@ivandev0, it would be very helpful to place a reference to the reasons for removing IR (de)serialization into the commit messages, a link to the corresponding YT issue, or just a few words. I have no active context about it, so it's difficult to make a meaningful approval. But even if I did, such a reference would still benefit the future maintenance.

Yes, sorry. I was a little bit lazy here. We don't have any tickets. Serialization of IR for JVM was an experimental feature for a long time, and the only known usage was at Google side. We finally got a green light to drop it completely.

As for the reason why we drop it, again, no tickets. The best thing I can give you is this comment.

Right now I am considering this as tech dept and have little to write into the commit message. I can create a ticket just for the sake of it, but I personally don't know the benefit of such a ticket.

Did a rebase on fresh master

/test-public

/dry-run

THIS IS A DRY RUN

Quality gate is triggered at https://buildserver.labs.intellij.net/build/892732140 — use this link to get full insight.

Quality gate was triggered with the following revisions:

kotlin
Branch: refs/merge/GITHUB-5693/safe-merge
Commit: 21be95e

Quality gate finished successfully.

/safe-merge

Quality gate is triggered at https://buildserver.labs.intellij.net/build/892992453 — use this link to get full insight.

Quality gate was triggered with the following revisions:

kotlin
Branch: refs/merge/GITHUB-5693/safe-merge
Commit: 8fb16cf

Quality gate finished successfully.